Peer-to-peer payment systems and methods

ABSTRACT

A method of including: receiving, from a sender, a group message directed toward the transfer facilitator and a recipient; identifying the sender and a payment account associated with the sender; parsing the group message to identify contact information for the recipient and instructions for a transfer request; contacting, using a private message and the parsed contact information, the recipient with instructions for receiving a payment from the sender; receiving, from the recipient, payment reception information including at least one of a recipient account or a payment method; and initiating, in accordance with the instructions for the transfer request, a fund transfer from the sender to the recipient from the identified payment account associated with the sender and the received payment reception information.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority under 35U.S.C. § 120 to, U.S. patent application Ser. No. 15/872,683, filed Jan.16, 2018, the entire contents of which are fully incorporated herein byreference.

FIELD

The present disclosure relates to peer-to-peer payment systems andmethods, and more particularly to the use of group messaging inpeer-to-peer payments.

BACKGROUND

With the decline in the use of physical money, electronic peer-to-peerpayment systems have become increasingly relevant tool. However, relatedart systems require both the sender and the receiver to be registered onthe same platform or have accounts with the same institution to processthe payments. Such requirements may be cumbersome to users. For example,in order to send or receive money, the sender and receiver mustcoordinate to select a platform and exchange contact information (e.g.,usernames) for that platform. If either the sender or receiver does notalready have an account, they must set up the account which can includeproviding personal information and financial account information to anunknown third party.

Accordingly, there is needed a method and system for initiatingfinancial transfers in a peer-to-peer manner that does not require theburdensome platform and coordination requirements. Embodiments of thepresent disclosure are directed to this and other considerations.

SUMMARY

Disclosed embodiments provide systems and methods using dual-stageneural network pipelines for detecting and recognizing specializedcharacters.

Consistent with the disclosed embodiments, various methods and systemsare disclosed. In an embodiment, a method for initiating a peer-to-peerpayment using group messaging is disclosed. The method may beimplemented with a computing device. The method may include executing anapplication configured to initiate a peer-to-peer fund transfer request;receiving, by the application, an indication for a request to transfermoney from a transferor to a recipient; receiving contact informationfor the recipient; generating, based on the received indication for therequest and according to a text messaging protocol, a group messageinstructing the transfer of money from the transferor to the recipient,the group message being from the transferor and to the recipient and atransfer facilitator, the transfer facilitator being configured tofacilitate the transfer of money; and transmitting the group message tothe recipient and the transfer facilitator.

The method may include receiving the contact information for therecipient by: accessing, by the application, a list of one or morecontacts of the transferor; receiving an indication of a user selectionof a contact from the list of one or more contacts; and extractingcontact information associated with the selected contact as the contactinformation for the recipient.

The method may further include transmitting, under the direction of theapplication, a verification message to the transfer facilitatorindicating validity of the group message instructing the transfer ofmoney.

The method may further include receiving, by the application, log-incredentials verifying the identity of the transferor, wherein theverification message verifies, to the transfer facilitator, the requestto transfer money.

The method may further include inserting, into the group message, averification code to validate an authenticity of the group message,wherein the verification message includes the verification code.

The method may further include receiving, by the application, thecontact information for the recipient and a transfer amount.

The method may further include receiving, by the application, anindication of an instruction to transmit the transfer request; andautomatically generating and transmitting the group message in responseto receiving the indication to transmit the transfer request.

The method may further include receiving, by the application, anindication for request to transfer money from a transferor to aplurality of recipients, wherein the group message instructs thetransfer of money from the transferor to the plurality of recipients,the group message being from the transferor and to the plurality ofrecipients and a transfer facilitator.

The method may further include receiving, from the transfer facilitator,a communication seeking confirmation of an interpretation of thetransfer request generated by the transfer facilitator, theinterpretation including an identification of the recipient and anamount to be transferred; and transmitting, in response to receiving anindication of a confirmation, a confirmation message to the transferfacilitator, the confirmation message indicating validation of theinterpretation.

According to some embodiments, there is a provided a method of atransfer facilitator including: receiving, from a sender, a groupmessage directed toward the transfer facilitator and a recipient;identifying the sender and a payment account associated with the sender;parsing the group message to identify contact information for therecipient and instructions for a transfer request; contacting, using aprivate message and the parsed contact information, the recipient withinstructions for receiving a payment from the sender; receiving, fromthe recipient, payment reception information including at least one of arecipient account or a payment method; and initiating, in accordancewith the instructions for the transfer request, a fund transfer from thesender to the recipient from the identified payment account associatedwith the sender and the received payment reception information.

In some cases, contacting the recipient with instructions for receivinga payment from the sender may include: generating, in response toreceiving the group message, a dynamic webpage with fields for receivingthe payment reception information; and transmitting, within the privatemessage, a link to the generated dynamic webpage.

The method may further include deleting the dynamic webpage in responseto either receiving the payment reception information or a timeoutoccurring.

The method may further include: receiving, from the recipient, imagedata of an image of an identification of the recipient; and analyzingthe image data to confirm an identify of the recipient.

In some cases, receiving payment reception information may include:receiving, from the recipient, image data of an image of a check; andextracting account information from the image data as the paymentreception information.

According to some implementations, the group message is directed towardthe transfer facilitator and a plurality of recipients, and the methodmay further include: parsing the group message to identify contactinformation for each of the plurality of recipients; contacting, using arespective private message between the transfer facilitator and each ofthe plurality of recipients, each of the plurality of recipients withinstructions for receiving a payment from the sender; receiving, fromeach of the plurality of recipients, respective payment receptioninformation; and initiating, in accordance with the instructions for thetransfer request, a fund transfer from the sender to each of theplurality of recipients using the identified payment account associatedwith the sender and the respective payment reception information.

According to some embodiments, the group message includes a header andbody, the header includes contact information for each of the pluralityof recipients, and the body includes names associated with respectivetransfer amounts corresponding to each of the plurality of recipients,and the method further includes: matching the names to the contactinformation; and initiating a fund transfer to each of the plurality ofrecipients includes initiating a fund transfer to each of the pluralityof recipients to for the respective transfer amount corresponding to therespective recipient.

According to some embodiments, there is a provided a method including:implementing a conversational bot for facilitating transfer requests;receiving, from a sender, a telephony group message directed towards theconversational bot and a recipient, the group message including a fundstransfer request from the sender to the recipient; parsing the groupmessage to identify contact information of the recipient; outputting, tothe recipient based on the identified contact information, a paymentrecovery message requesting information on delivering payment to therecipient, a body of the payment recovery message being determined bythe conversational bot; receiving, from the recipient, payment receptioninformation; and initiating, in accordance with the funds transferrequest, a fund transfer from the sender to the recipient based on thepayment reception information.

According to some embodiments, the telephony group message is directedtowards the conversational bot and a plurality of recipients, a body ofthe group message includes a funds transfer request to transferrespective specified amounts to each of the recipients, and the methodfurther includes analyzing, using the conversational bot, the body ofthe group message to determine an amount of money to be transferred tothe respective recipients.

The method may further include identifying, from the group message,contact information of the sender; determining an identity of the senderbased on the contact information; and determining a payment accountassociated with the sender for transferring funds to the recipient inaccordance with the funds transfer request.

The method may further include determining an identity of the sender anddetermining a payment account by reference to a financial institutiondatabase.

Consistent with the disclosed embodiments, systems and non-transitorycomputer readable mediums for providing dual-stage neural networkpipelines for detecting and recognizing specialized characters.

Further features of the disclosed design, and the advantages offeredthereby, are explained in greater detail hereinafter with reference tospecific embodiments illustrated in the accompanying drawings, whereinlike elements are indicated be like reference designators.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and which are incorporated into andconstitute a portion of this disclosure, illustrate variousimplementations and aspects of the disclosed technology and, togetherwith the description, serve to explain the principles of the disclosedtechnology. In the drawings:

FIG. 1 is a diagram of an example system environment that may be used toimplement one or more embodiments of the present disclosure;

FIG. 2 is a component diagram of a service provider terminal accordingto an example embodiment;

FIG. 3 is a component diagram of a sender computing device according toan example embodiment;

FIG. 4 is a timing diagram of a funds transfer method using group textaccording to an example embodiment;

FIG. 5 is an example group text structure according to an exampleembodiment;

FIG. 6 is a flowchart of generating a group message in accordance withan example embodiment; and

FIG. 7 is a flowchart of initiating a funds transfer in accordance withan example embodiment.

DETAILED DESCRIPTION

Some implementations of the disclosed technology will be described morefully with reference to the accompanying drawings. This disclosedtechnology may, however, be embodied in many different forms and shouldnot be construed as limited to the implementations set forth herein. Thecomponents described hereinafter as making up various elements of thedisclosed technology are intended to be illustrative and notrestrictive. Many suitable components that would perform the same orsimilar functions as components described herein are intended to beembraced within the scope of the disclosed electronic devices andmethods. Such other components not described herein may include, but arenot limited to, for example, components developed after development ofthe disclosed technology.

It is also to be understood that the mention of one or more method stepsdoes not preclude the presence of additional method steps or interveningmethod steps between those steps expressly identified. Similarly, it isalso to be understood that the mention of one or more components in adevice or system does not preclude the presence of additional componentsor intervening components between those components expressly identified.

The present disclosure is directed to methods and systems forpeer-to-peer payments, and, in particular, for utilizing group messagingto initiate peer-to-peer payments. In one embodiment, a specializedapplication associated with a financial service provider is used togenerate and transmit the group text message. A user may activate theapplication, indicate it would like to transfer funds, and provide fundsinstructions and contact information for a recipient. The applicationmay generate a group text message based on the instructions and send thesame to the recipient and a transfer facilitator.

In another embodiment, a system may include one or more memory devicesstoring instructions, and one or more processors configured to executethe instructions to perform steps of a method of initiating apeer-to-peer payment as disclosed herein.

In another embodiment, a non-transitory computer-readable medium isdisclosed. The non-transitory computer-readable medium may storeinstructions that, when executed by one or more processors, cause asystem to execute a method of generating a text message or facilitatinga funds transfer.

Reference will now be made in detail to example embodiments of thedisclosed technology, examples of which are illustrated in theaccompanying drawings and disclosed herein. Wherever convenient, thesame references numbers will be used throughout the drawings to refer tothe same or like parts.

FIG. 1 is a diagram of an example system environment that may be used toimplement one or more embodiments of the present disclosure. Thecomponents and arrangements shown in FIG. 1 are not intended to limitthe disclosed embodiments as the components used to implement thedisclosed processes and features may vary.

In accordance with disclosed embodiments, system environment 100 mayinclude a service provider terminal 110 in communication with a sendercomputing device 120 and a recipient computing device 130 via telephonynetwork 103 and/or data network 106. In some embodiments, serviceprovider terminal 110 may also be in communication with variousdatabases (e.g., banking databases). Sender computing device 120 andrecipient computing device 130 may be respective mobile computingdevices (e.g., a smart phone, tablet computer, smart wearable device,portable laptop computer, voice command device, wearable augmentedreality device, or other mobile computing device) or stationary devices(e.g., desktop computer).

In some embodiments, the sender computing device 120 may transmit agroup message to the service provider terminal 110 and recipientcomputing device 130 authorizing a transfer of money to the user of therecipient computing device over telephony network 103. As discussedbelow in greater detail, the group message may be generated and/or sentusing an application associated with a financial service provider. Inresponse to receiving the group message, the service provider terminal110 may communicate with recipient computing device 130 over thetelephony network 103 and/or data network 106 to affect the moneytransfer. In some embodiments, the server provider terminal 110 mayimplement a conversational bot to interpret the group message from thesender computing device 120 and communicate with the recipient computingdevice 130

Telephony network 103 may be any suitable network for exchanging grouptext messages. In some embodiments, telephony network 103 may include acellular network. Network 106 may be of any suitable type, includingindividual connections via the internet such as cellular or WiFinetworks. In some embodiments, network 105 may connect terminals usingdirect connections such as radio-frequency identification (RFID),near-field communication (NFC), Bluetooth™, low-energy Bluetooth™ (BLE),WiFi™, ZigBee™, ambient backscatter communications (ABC) protocols, USB,or LAN. Because the information transmitted may be personal orconfidential, security concerns may dictate one or more of these typesof connections be encrypted or otherwise secured. In some embodiments,however, the information being transmitted may be less personal, andtherefore the network connections may be selected for convenience oversecurity

An example embodiment of service provider terminal 110 is shown in moredetail in FIG. 2. Sender computing device 120 and recipient computingdevice 130 may have a similar structure and components that are similarto those described with respect to service provider terminal 110. Asshown, service provider terminal 110 may include a processor 210, aninput/output (“I/O”) device 220, a memory 230 containing an operatingsystem (“OS”) 240 and a program 250. For example, service providerterminal 110 may be a single server or may be configured as adistributed computer system including multiple servers or computers thatinteroperate to perform one or more of the processes and functionalitiesassociated with the disclosed embodiments. In some embodiments, serviceprovider terminal 110 may further include a peripheral interface, atransceiver, a mobile network interface in communication with processor210, a bus configured to facilitate communication between the variouscomponents of the service provider terminal 110, and a power sourceconfigured to power one or more components of service provider terminal110.

A peripheral interface may include the hardware, firmware and/orsoftware that enables communication with various peripheral devices,such as media drives (e.g., magnetic disk, solid state, or optical diskdrives), other processing devices, or any other input source used inconnection with the instant techniques. In some embodiments, aperipheral interface may include a serial port, a parallel port, ageneral-purpose input and output (GPIO) port, a game port, a universalserial bus (USB), a micro-USB port, a high definition multimedia (HDMI)port, a video port, an audio port, a Bluetooth™ port, a near-fieldcommunication (NFC) port, another like communication interface, or anycombination thereof.

In some embodiments, a transceiver may be configured to communicate withcompatible devices and ID tags when they are within a predeterminedrange. A transceiver may be compatible with one or more of:radio-frequency identification (RFID), near-field communication (NFC),Bluetooth™, low-energy Bluetooth™ (BLE), WiFi™, ZigBee™ ambientbackscatter communications (ABC) protocols or similar technologies.

A mobile network interface may provide access to a cellular network, theInternet, or another wide-area network. In some embodiments, a mobilenetwork interface may include hardware, firmware, and/or software thatallows processor(s) 210 to communicate with other devices via wired orwireless networks, whether local or wide area, private or public, asknown in the art. A power source may be configured to provide anappropriate alternating current (AC) or direct current (DC) to powercomponents.

As described above, service provider terminal 110 may configured toremotely communicate with one or more other devices, such as sendercomputing device 120 and recipient computing device. According to someembodiments, service provider terminal 110 may utilize a dual-stageneural network pipeline to detect and recognize textual information.

Processor 210 may include one or more of a microprocessor,microcontroller, digital signal processor, co-processor or the like orcombinations thereof capable of executing stored instructions andoperating upon stored data. Memory 230 may include, in someimplementations, one or more suitable types of memory (e.g. such asvolatile or non-volatile memory, random access memory (RAM), read onlymemory (ROM), programmable read-only memory (PROM), erasableprogrammable read-only memory (EPROM), electrically erasableprogrammable read-only memory (EEPROM), magnetic disks, optical disks,floppy disks, hard disks, removable cartridges, flash memory, aredundant array of independent disks (RAID), and the like), for storingfiles including an operating system, application programs (including,for example, a web browser application, a widget or gadget engine, andor other applications, as necessary), executable instructions and data.In one embodiment, the processing techniques described herein areimplemented as a combination of executable instructions and data withinthe memory 230.

Processor 210 may be one or more known processing devices, such as amicroprocessor from the Pentium™ family manufactured by Intel™ or theTurion™ family manufactured by AMD™. Processor 210 may constitute asingle core or multiple core processor that executes parallel processessimultaneously. For example, processor 210 may be a single coreprocessor that is configured with virtual processing technologies. Incertain embodiments, processor 210 may use logical processors tosimultaneously execute and control multiple processes. Processor 210 mayimplement virtual machine technologies, or other similar knowntechnologies to provide the ability to execute, control, run,manipulate, store, etc. multiple software processes, applications,programs, etc. One of ordinary skill in the art would understand thatother types of processor arrangements could be implemented that providefor the capabilities disclosed herein.

Service provider terminal 110 may include one or more storage devicesconfigured to store information used by processor 210 (or othercomponents) to perform certain functions related to the disclosedembodiments. In one example, service provider terminal 110 may includememory 230 that includes instructions to enable processor 210 to executeone or more applications, such as server applications, networkcommunication processes, and any other type of application or softwareknown to be available on computer systems. Alternatively, theinstructions, application programs, etc. may be stored in an externalstorage or available from a memory over a network. The one or morestorage devices may be a volatile or non-volatile, magnetic,semiconductor, tape, optical, removable, non-removable, or other type ofstorage device or tangible computer-readable medium.

In one embodiment, service provider terminal 110 may include memory 230that includes instructions that, when executed by processor 210, performone or more processes consistent with the functionalities disclosedherein. Methods, systems, and articles of manufacture consistent withdisclosed embodiments are not limited to separate programs or computersconfigured to perform dedicated tasks. For example, service providerterminal 110 may include memory 230 that may include one or moreprograms 250 to perform one or more functions of the disclosedembodiments. Moreover, processor 210 may execute one or more programs250 located remotely from service provider terminal 110. For example,service provider terminal 110 may access one or more remote programs250, that, when executed, perform functions related to disclosedembodiments.

Memory 230 may include one or more memory devices that store data andinstructions used to perform one or more features of the disclosedembodiments. Memory 230 may also include any combination of one or moredatabases controlled by memory controller devices (e.g., server(s),etc.) or software, such as document management systems, Microsoft™ SQLdatabases, SharePoint™ databases, Oracle™ databases, Sybase™ databases,or other relational databases. Memory 230 may include softwarecomponents that, when executed by processor 210, perform one or moreprocesses consistent with the disclosed embodiments. In someembodiments, memory 230 may include an image processing database 260 anda neural-network pipeline database 270 for storing related data toenable service provider terminal 110 to perform one or more of theprocesses and functionalities associated with the disclosed embodiments.

Service provider terminal 110 may also be communicatively connected toone or more memory devices (e.g., databases (not shown)) locally orthrough a network. The remote memory devices may be configured to storeinformation and may be accessed and/or managed by service providerterminal 110. By way of example, the remote memory devices may bedocument management systems, Microsoft™ SQL database, SharePoint™databases, Oracle™ databases, Sybase™ databases, or other relationaldatabases. Systems and methods consistent with disclosed embodiments,however, are not limited to separate databases or even to the use of adatabase.

Service provider terminal 110 may also include one or more I/O devices220 that may include one or more interfaces for receiving signals orinput from devices and providing signals or output to one or moredevices that allow data to be received and/or transmitted by serviceprovider terminal 110. For example, service provider terminal 110 mayinclude interface components, which may provide interfaces to one ormore input devices, such as one or more keyboards, mouse devices, touchscreens, track pads, trackballs, scroll wheels, digital cameras,microphones, sensors, and the like, that enable service providerterminal 110 to receive data from one or more users (such as via sendercomputing device 120 and recipient computing device 130).

In example embodiments of the disclosed technology, service providerterminal 110 may include any number of hardware and/or softwareapplications that are executed to facilitate any of the operations. Theone or more I/O interfaces may be utilized to receive or collect dataand/or user instructions from a wide variety of input devices. Receiveddata may be processed by one or more computer processors as desired invarious implementations of the disclosed technology and/or stored in oneor more memory devices.

While service provider terminal 110 has been described as one form forimplementing the techniques described herein, those having ordinaryskill in the art will appreciate that other, functionally equivalenttechniques may be employed. For example, as known in the art, some orall of the functionality implemented via executable instructions mayalso be implemented using firmware and/or hardware devices such asapplication specific integrated circuits (ASICs), programmable logicarrays, state machines, etc. Furthermore, other implementations of theterminal 110 may include a greater or lesser number of components thanthose illustrated.

In some cases, the service provider terminal 110 may be embodied in asingle device (e.g., a server). In other cases, a plurality of devicesmay work to provide the functionality of the describes service providerterminal 110.

FIG. 3 shows an example embodiment of a sender computing device 120. Asshown, sender computing device 120 may include input/output (“I/O”)device 220 for receiving data from another device (e.g., serviceprovider terminal 110), memory 230 containing operating system (“OS”)240, program 250, and any other associated component as described abovewith respect to service provider terminal 110. Sender computing device120 may also have one or more processors 210, a geographic locationsensor (“GLS”) 304 for determining the geographic location of sendercomputing device 120, a display 306 for displaying content such as textmessages, images, and selectable buttons/icons/links, an environmentaldata (“ED”) sensor 308 for obtaining environmental data including audioand/or visual information, and a user interface (“U/I”) device 310 forreceiving user input data, such as data representative of a click, ascroll, a tap, a press, or typing on an input device that can detecttactile inputs. User input data may also be non-tactile inputs that maybe otherwise detected by ED sensor 308. For example, user input data mayinclude auditory commands. According to some embodiments, U/I device 310may include some or all of the components described with respect toinput/output device 220 above. In some embodiments, environmental datasensor 308 may include a microphone and/or an image capture device, suchas a digital camera.

Components of recipient computing device 130 may be substantiallysimilar to those describes with respect to sender computing device 120.Accordingly, a detailed description is not repeated for compactness.

FIG. 4 shows a timing diagram 400 of a fund transfer according to anexample embodiment. At 405, the sender computing device 120 generatesand transmits a group message to the service provider terminal 110. Insome cases, the sender computing device 120 may execute an applicationand generate the group message in accordance with commands from theapplication. A method of generating the group message is described inmore detail below with reference to FIG. 6. The group message may besent using a text messaging protocol. FIG. 5 illustrates a structure ofthe group message according to an example embodiment. The group message500 includes a header 510 and a body 520. The header includes contactinformation from the sender 512 (i.e., a telephone number associatedwith the sender computing device 120) and the recipients 514, 516 (i.e.,telephone numbers associated with service provider terminal 110 and therecipient computing device 130). The body 520 of the text messageincludes payment instructions 522 for the service provider terminal 110to provide a payment to a user of the recipient computing device 130. Insome embodiments, the body 520 may include a verification code 524 forverifying an authenticity of the payment instructions 522. Asnon-limiting examples, the verification code 524 may be a hash valuecreated based on one or more of a time of submission, a transfer amount,sender contact information 512, recipient contact information 516, andan account associated with the sender contact information 512.

Referring back to FIG. 4, at 410, the service provider terminal 110parses the group message to identify contact information of the sender512 and recipient 516, and the payment instructions 522. If included,the service provider terminal 110 may also identify the verificationcode 524 and verify the authenticity of the payment instructions 522. At415, the service provider terminal 110 determines, based on the sendercontact information, an account associated with a user of the sendercomputing device 120, and accesses the account to determine if there aresufficient funds to fulfill the payment instructions 522.

At 420, if the account has sufficient funds, the service providerterminal 110 generates a dynamic web page. In some embodiments, thedynamic web page is uniquely linked or associated with the paymentrequest. The dynamic web page may have input fields for receivingpayment reception information (e.g., recipient account information orrecipient address information). In some cases, the dynamic web page maybe accessible for a limited time (e.g., 24 hours) before the web page isdeleted or deactivated. At 425, the service provider terminal 110transmits a link to the dynamic web page to the recipient computingdevice 130. The link may be sent using a private message, for example,using a text message protocol with the recipient computing device 130 asthe only recipient.

At 430, the recipient computing device 130 receives an indication tofollow the link to the dynamic web page, for example, from user input.At 435, payment reception information is transmitted to the serviceprovider terminal 110 from the recipient computing device 130 using thedynamic web page. At 440, the service provider terminal 110 initiates atransfer from the account associated with the user of the sendercomputing device 120 to a user of the recipient computing device 130 inaccordance with the payment instructions 522. At 445, the serviceprovider terminal 110 notifies the sender computing device 120 and therecipient computing device 130 of the payment initiation.

FIG. 6 illustrates a method 600 of generating a group message inaccordance with an example embodiment. The method 600 may be performedby the sender computing device 120. At 605, the sender computing device120 executes or launches an application. The application may includefunctionalities to generate a funds transfer request. In some cases, theapplication may verify an identity of the user of the sender computingdevice 120, for example, by requiring log-in credentials. In someembodiments, the application may be associated with a financialinstitution and/or the service provider terminal 110. At 610, the sendercomputing device 120 receives an indication for a request to transferfunds. The indication may be input into the application. In some cases,the application may present a graphical user interface configured toreceive user input designated for initiating fund transfers.

At 615, the sender computing device 120 receives contact information fora recipient computing device 130 and fund transfer parameters (e.g., howmuch, when, where, form of payment, etc.). The contact information maybe received by user input. In some cases, the application may accesscontact information of a user of the sender computing device 120. Forexample, the sender computing device 120 may access and display a listcontacts stored on the sender computing device 120, receive anindication of a selection of a contact from the list of contacts, andextract contact information of the selected contact (i.e., the recipientcomputing device 130).

At 620, based on this information, the sender computing device 120generates the group message according to a text messaging protocol. Thegroup message may be directed to the service provider terminal 110 andthe recipient computing device 130. The group message 500 may instructthe service provider terminal 110 to transfer funds to a user of therecipient computing device 130 in accordance with the paymentinstructions 522 included in the group message 500.

In some cases, at 625, the sender computing device 120 performs transferrequest validation. For example, in some embodiments, the sendercomputing device 120 (i.e., the application executing on the sendercomputing device 120) generates a verification code 524 and inserts theverification code 524 into the body 520 for the group message 500. Theverification code 524 may be a hash value calculated based on, asnon-limiting examples, account information associated with a user of thesender computing device 120, contact information associated with thesender computing device 120 or the recipient computing device 130,log-in credentials to the application, a transfer amount, and a valueprovided by the application. The verification code 524 may bepseudo-randomly generated by the sender computing device 120 (e.g., bythe application).

In some implementations, the sender computing device 120 may establish aconnection with the service provider terminal 110 and transmit averification message to the service provider terminal 110 over theconnection. In some cases, the verification message may merely indicatethat a transfer is being requested from the user of the sender computingdevice. In some embodiments, the verification message may include theverification code 524.

At 630, the group message 500 is transmitted to the recipient computingdevice 130 and the service provider terminal 110. In some cases, thegroup message 500 may be generated and displayed before transmitting thegroup message 500. In other implementations, the group message 500 maybe automatically generated and transmitted in response to receiving thecontact information for the recipient computing device.

In some cases, at 635, the sender computing device 120 may receive andrespond to a confirmation request from the service provider terminal110. As a non-limiting example, the service provider terminal 110 mayattempt to interpret an intent to the payment instructions 522, andprovide the interpretation to the service provider terminal 110 forverification. The service provider terminal 110 may transmit aconfirmation message or an objection message based on a review of theinterpretation.

Although the group message 500 is discussed as being sent to a singularrecipient computing device 130, this is merely an example. In somecases, the group message 500 may be directed to a plurality of recipientcomputing devices 130 and the service provider terminal 110. The groupmessage 500 may include individual payment instructions 522 for each ofthe recipient computing devices 130 or group payment instructions (notshown). The service provider terminal 110 is configured to interpret thepayment instructions 522 for one or more recipient computing devices130. Example payment instructions are described below with reference toTable 1.

TABLE 1 Payment Instruction Message Recipients Interpretation Please payAndrew $50 Andrew Transfer $50 from Sender to Service Provider TerminalAndrew Please pay Andrew and Andrew Transfer $50 from Sender to Stepheneach $50 Stephen Andrew Service Provider Terminal Transfer $50 fromSender to Stephen Please split $50 between Andrew Transfer $25 fromSender to Andrew and Stephen Stephen Andrew Service Provider TerminalTransfer $25 from Sender to Stephen Please pay Andrew $50 and AndrewTransfer $50 from Sender to Stephen $25 Stephen Andrew Service ProviderTerminal Transfer $25 from Sender to Stephen Please pay Andrew my ⅓ ofAndrew Transfer $30 from Sender to $90 Service Provider Terminal Andrew

FIG. 7 illustrates a method 700 of initiating a funds transfer inaccordance with an example embodiment. The method 700 may be performedby the service provider terminal 110 (e.g., a transfer facilitator). At705, the service provider terminal 110 receives a group message (e.g.,group message 500) sent to the service provider terminal 110 and arecipient computing device 130 from the sender computing device 120. At710, the service provider terminal 110 identifies the sender. Forexample, the service provider terminal 110 may parse the group messageto determine a phone number of the sender (e.g., the sender computingdevice 120) and identify the sender by comparing the phone number of thesender to records maintained by the service provider terminal 110. Insome cases, the service provider terminal 110 may be associated with afinancial service provider (e.g., a bank), and a user of the sendercomputing device 120 may be a customer of the financial serviceprovider.

In some cases, the service provider terminal 110 may identify the senderbased on information included within the group message 500. For example,the service provider terminal 110 may parse the group message to locateencoded information indicating one or more of the sender (e.g., thesender computing device 120) or the sender account. The encodedinformation may be generated by, for example, an application thatgenerates the group message on the sender computing device 120. In somecases, the application may be an application associated with thefinancial service provider, and require a user log-in before generatingthe group message with the encoded information. In some cases, theencoded information may be a hash value based on one or more of thesender and the sender account.

At 715, the service provider terminal 110 identifies a payment accountassociated with the sender (i.e., the sender computing device 120). Forexample, the payment account may be a savings account, a checkingaccount, or a credit card account. In some cases, the service providerterminal 110 may associated with a financial service provider (e.g., abank), and the payment account may be an account at the financialservice provider. At 720, the service provider terminal 110 parses thegroup message to identify contact information for the recipient (i.e.,the recipient computing device 130). For example, group message 500 mayinclude a header information indicating that the group message 500 wasdirected to one or more entities other than the service providerterminal 110. For example, the service provider terminal 110 may parsethe group message to determine a phone number of the intended recipient(e.g., a user of the recipient computing device 120).

At 725, the service provider terminal 110 parses the message to retrieveinstructions for a transfer request. As discussed above, theinstructions may direct the service provider terminal 110 to initiate atransfer from the sender (i.e., a user of the sender computing device120) to the recipient (i.e., a recipient computing device 130).

At 730, the service provider terminal 110 may validate the instructions.For example, the service provider terminal 110 may receive a validationmessage from the sender computing device 120 in addition to the groupmessage 500. The validation message may be sent over a secure connectionformed between the sender computing device 120 and a server of afinancial institution associated with the service provider terminal 110.For example, the sender computing device 120 may execute an applicationrequiring log-in credentials. The application may automatically transmita validation message when a group message 500 is generated by the sendercomputing device 120. In some embodiments, a validation code may beincluded in the group message 500. For example, the validation code maybe generated by the sender computing device 120 and/or received by thesender computing device 120 from the financial institution associatedwith the service provider terminal 110. As discussed above, in somecases, the validation code may be a hash value of one or more aspectsassociated with the request. The service provider terminal 110 may parsethe group message 500 to identify the validation code and verify thecode, for example, by comparing the code to a stored or calculatedvalue.

At 735, the service provider terminal 110 may generate a dynamic webpagewith fields for receiving payment reception information or request thedynamic web page to be generated. The dynamic webpage may have arandomized URL. The dynamic web page and/or URL may be uniquelyassociated with the transfer request, such as via association with aunique identifier or the validation code. In some cases, the dynamic webpage may require log-in credentials. In some implementations, thedynamic webpage may only be accessible from certain locations (e.g., GPSlocations of the recipient computing device 130).

At 740, the service provider terminal 110 generates a private messageand contacts the recipient (e.g., the recipient computing device 130)using the private message according to the parsed contact information ofthe intended recipient. For example, the service provider terminal 110may output the private message using a text message protocol to theidentified phone number of the intended recipient. The private messagecontains instructions for receiving a payment from the sender. Forexample, the private message may include a link to the generated dynamicwebpage. As necessary, the private message may include log-incredentials.

At 745, the service provider terminal 110 may determine whether atimeout has occurred. At 765, if the timeout has occurred, the dynamicwebpage is deleted. As a non-limiting example, the dynamic webpage mayonly be available for 12 hours. After 12 hours, the dynamic webpage willbe deleted.

At 750 the service provider terminal 110 receives payment receptioninformation from the recipient according to the instructions in theprivate message. In some cases, the recipient navigates to the dynamicwebpage using the recipient computing device 130 and enters paymentinformation into the dedicated fields. As non-limiting examples, therecipient may request a check be delivered to a particular address, afunds transfer into a specific account, the funds added to a prepaidcard, or the funds be received through one or more third-party paymentmechanisms (e.g., Zelle, PayPal, or Venmo) or platforms. In certaininstances, the one or more third-party payment mechanisms may bepresented in the webpage and limited to third-party payment mechanismswith which the sender has an account. In some cases, the one or morethird-party payment mechanisms may be limited to third-party paymentmechanisms with which the sender and the receive both have an account.In some instances, the service provider terminal 110 may receive thepayment reception information in the form of a picture of a check. Forexample, the recipient may upload a picture of a check to the dynamicwebpage, and the service provider terminal 110 may extract one or moreof the account number, account holder, and routing information from thecheck image. In other embodiments, the service provider terminal 110 mayreceive the payment reception information in the form of a picture of apayment card or other means from which account information can bedetermined. In some embodiments, the dynamic webpage may be configuredwith functionality to activate a camera of the recipient computingdevice 130 to automatically capture and upload an image from whichpayment reception information can be determined.

At 755, the service provider terminal 110 may receive identificationinformation of the recipient. For example, the recipient may upload animage of an identification (e.g., driver's ID or passport) that mayconfirm the identity of the recipient as the intended recipient.

At 760, the service provider terminal 110 initiates a funds transferfrom the sender to the recipient in accordance with the instructions inthe group message 500, the identified payment account associated withthe sender and the received payment reception information from therecipient. The transfer of funds may be initiated via one or moretransfer mechanisms determined based on the payment receptioninformation, which in some instances may identify a particular mechanism(e.g., debit transfer, intrabank transfer, mailed check) or service(which may include a third-party service) for handling payments and fundtransfers.

At 765, after receiving the payment reception information and/or thetimeout occurring, the dynamic webpage is deleted. At 770, the serviceprovider terminal 110 may transmit a message indicating the state of thefunds transfer. For example, if a timeout occurs before receiving thepayment reception information, the service provider terminal 110 maycontact the sender computing device 120 and the recipient computingdevice 130 to indicate that the funds transfer did not occur. If thefunds transfer is initiated, the service provider terminal 110 maycontact the sender computing device 120 and the recipient computingdevice 130 to indicate that the funds transfer has been initiated.

In some cases, as discussed above, the group message may be directed aplurality of intended recipients. The service provider terminal 110 mayidentify contact information for each of the plurality of recipients,determine payment instructions for each of the plurality of recipients,generate, and contact each recipient using a respective private messagebetween the service provider terminal 110 and each recipient computingdevices 130. Individual dynamic webpages may be generated for each ofthe plurality of recipients to receive respective payment receptioninformation. The body of the message may include names and valuesrelated to respective recipients. The service provider terminal 110 maymatch the names to the respective recipient contact information from theheader. For example, if the payment instructions state “Please payAndrew $50 and Stephen $25,” the service provider terminal 110 may checkits records to determine if the contact information for either recipientmatches its records for an “Andrew” or a “Stephen.”

According to some implementations, the service provider terminal 110 mayrequest clarification of the payment instructions. For example, if thegroup message is to a plurality of recipients for different values, theservice provider terminal 110 may transmit a request to the sendercomputing device 120 to identify which contact information correspondsto which recipient.

In some cases, the service provider terminal 110 may implement aconversational bot. The conversational bot may parse and interpret thegroup message 500, and prepare the private message, the notificationmessages, and the clarification requests.

In some cases, the service provider terminal 110 may facilitate paymenttransfers using on one or more third party mechanisms (e.g., Zelle,Venmo, or PayPal). For example, the sender and recipient may each haveone or more accounts with a third-party payment mechanism. The serviceprovider terminal 110 may identify a third-party payment mechanism withwhich both the sender and receiver have an account, the service providerterminal 110 may generate a private message (and contact the recipientusing the private message) that inquires whether the recipient wouldlike to receive payment using the identified third-party paymentmechanism. In some cases, the service provider terminal 110 may onlyidentify one or more third-party payment mechanisms with which thesender has an account, and the service provider terminal 110 maygenerate a private message (and contact the recipient using the privatemessage) that inquires whether the recipient would like to receivepayment using the identified one or more third-party payment mechanisms.In some instances, the private message may include the instructions forreceiving a payment from the sender, with, for example, a link to thegenerated dynamic webpage discussed above with reference to FIG. 7 alongwith the inquiry about the identified third-party payment mechanism. Insome cases, the inquiry may include a link to an application associatedwith the identified third-party payment mechanism. In a case where thegroup message is directed to a plurality of recipients, the serviceprovider terminal 110 may customize third-party payment mechanismoptions for each recipient based on third-party mechanisms with whichboth the sender and the individual recipient have an account.Accordingly, in some cases, each recipient may receive funds via anavailable mechanism (including a third-party mechanism) that they aremost interested in.

As used in this application, the terms “component,” “module,” “system,”“server,” “processor,” “memory,” and the like are intended to includeone or more computer-related units, such as but not limited to hardware,firmware, a combination of hardware and software, software, or softwarein execution. For example, a component may be, but is not limited tobeing, a process running on a processor, an object, an executable, athread of execution, a program, and/or a computer. By way ofillustration, both an application running on a computing device and thecomputing device can be a component. One or more components can residewithin a process and/or thread of execution and a component may belocalized on one computer and/or distributed between two or morecomputers. In addition, these components can execute from variouscomputer readable media having various data structures stored thereon.The components may communicate by way of local and/or remote processessuch as in accordance with a signal having one or more data packets,such as data from one component interacting with another component in alocal system, distributed system, and/or across a network such as theInternet with other systems by way of the signal.

Certain embodiments and implementations of the disclosed technology aredescribed above with reference to block and flow diagrams of systems andmethods and/or computer program products according to exampleembodiments or implementations of the disclosed technology. It will beunderstood that one or more blocks of the block diagrams and flowdiagrams, and combinations of blocks in the block diagrams and flowdiagrams, respectively, can be implemented by computer-executableprogram instructions. Likewise, some blocks of the block diagrams andflow diagrams may not necessarily need to be performed in the orderpresented, may be repeated, or may not necessarily need to be performedat all, according to some embodiments or implementations of thedisclosed technology. One of ordinary skill will understand that theorder of certain elements of the block diagrams and flow diagrams may bealtered unless explicitly required to operate in a particular order.

These computer-executable program instructions may be loaded onto ageneral-purpose computer, a special-purpose computer, a processor, orother programmable data processing apparatus to produce a particularmachine, such that the instructions that execute on the computer,processor, or other programmable data processing apparatus create meansfor implementing one or more functions specified in the flow diagramblock or blocks. These computer program instructions may also be storedin a computer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-readablememory produce an article of manufacture including instruction meansthat implement one or more functions specified in the flow diagram blockor blocks.

As an example, embodiments or implementations of the disclosedtechnology may provide for a computer program product, including acomputer-usable medium having a computer-readable program code orprogram instructions embodied therein, said computer-readable programcode adapted to be executed to implement one or more functions specifiedin the flow diagram block or blocks. Likewise, the computer programinstructions may be loaded onto a computer or other programmable dataprocessing apparatus to cause a series of operational elements or stepsto be performed on the computer or other programmable apparatus toproduce a computer-implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide elementsor steps for implementing the functions specified in the flow diagramblock or blocks.

Accordingly, blocks of the block diagrams and flow diagrams supportcombinations of means for performing the specified functions,combinations of elements or steps for performing the specifiedfunctions, and program instruction means for performing the specifiedfunctions. It will also be understood that each block of the blockdiagrams and flow diagrams, and combinations of blocks in the blockdiagrams and flow diagrams, can be implemented by special-purpose,hardware-based computer systems that perform the specified functions,elements or steps, or combinations of special-purpose hardware andcomputer instructions.

Certain implementations of the disclosed technology are described abovewith reference to user devices may include mobile computing devices.Those skilled in the art recognize that there are several categories ofmobile devices, generally known as portable computing devices that canrun on batteries but are not usually classified as laptops. For example,mobile devices can include, but are not limited to portable computers,tablet PCs, internet tablets, PDAs, ultra-mobile PCs (UMPCs), wearabledevices, and smart phones. Additionally, implementations of thedisclosed technology can be utilized with internet of things (IoT)devices, smart televisions and media devices, appliances, automobiles,toys, and voice command devices, along with peripherals that interfacewith these devices.

In this description, numerous specific details have been set forth. Itis to be understood, however, that implementations of the disclosedtechnology may be practiced without these specific details. In otherinstances, well-known methods, structures and techniques have not beenshown in detail in order not to obscure an understanding of thisdescription. References to “one embodiment,” “an embodiment,” “someembodiments,” “example embodiment,” “various embodiments,” “oneimplementation,” “an implementation,” “example implementation,” “variousimplementations,” “some implementations,” etc., indicate that theimplementation(s) of the disclosed technology so described may include aparticular feature, structure, or characteristic, but not everyimplementation necessarily includes the particular feature, structure,or characteristic. Further, repeated use of the phrase “in oneimplementation” does not necessarily refer to the same implementation,although it may.

Throughout the specification and the claims, the following terms take atleast the meanings explicitly associated herein, unless the contextclearly dictates otherwise. The term “connected” means that onefunction, feature, structure, or characteristic is directly joined to orin communication with another function, feature, structure, orcharacteristic. The term “coupled” means that one function, feature,structure, or characteristic is directly or indirectly joined to or incommunication with another function, feature, structure, orcharacteristic. The term “or” is intended to mean an inclusive “or.”Further, the terms “a,” “an,” and “the” are intended to mean one or moreunless specified otherwise or clear from the context to be directed to asingular form. By “comprising” or “containing” or “including” is meantthat at least the named element, or method step is present in article ormethod, but does not exclude the presence of other elements or methodsteps, even if the other such elements or method steps have the samefunction as what is named.

As used herein, unless otherwise specified the use of the ordinaladjectives “first,” “second,” “third,” etc., to describe a commonobject, merely indicate that different instances of like objects arebeing referred to, and are not intended to imply that the objects sodescribed must be in a given sequence, either temporally, spatially, inranking, or in any other manner.

While certain embodiments of this disclosure have been described inconnection with what is presently considered to be the most practicaland various embodiments, it is to be understood that this disclosure isnot to be limited to the disclosed embodiments, but on the contrary, isintended to cover various modifications and equivalent arrangementsincluded within the scope of the appended claims. Although specificterms are employed herein, they are used in a generic and descriptivesense only and not for purposes of limitation.

This written description uses examples to disclose certain embodimentsof the technology and also to enable any person skilled in the art topractice certain embodiments of this technology, including making andusing any apparatuses or systems and performing any incorporatedmethods. The patentable scope of certain embodiments of the technologyis defined in the claims, and may include other examples that occur tothose skilled in the art. Such other examples are intended to be withinthe scope of the claims if they have structural elements that do notdiffer from the literal language of the claims, or if they includeequivalent structural elements with insubstantial differences from theliteral language of the claims.

Example Use Cases

The following example use cases describe examples of a typicalimplementation of the use of group text messages for funds transfer.These are intended solely for explanatory purposes and not inlimitation. In one case, a user activates a bank application andindicates that he would like to transfer money to a third party using agroup text using a smart phone (e.g., sender computing device 120). Thesmart phone, executing the application, may get contact information forthe third party and payment instructions (e.g., how much, what timeframe, from what account). The smart phone may generate and transmit agroup text message to a transfer facilitator (e.g., service providerterminal 110) and the third-party (e.g., recipient computing device130). In some cases, the smart phone may also receive and/or generatevalidation information and send the same to the transfer facilitator.The transfer facilitator determines a payment account associated withthe user (e.g., a bank account held by the bank) and separately contactsthe third-party to determine how they would like to be paid (e.g.,account transfer, mailed check). The transfer facilitator initiates thetransfer from the payment account in the manner identified by thethird-party and in accordance with the payment instructions in the grouptext message.

In another case, a financial institution server (e.g., server providerterminal 110) receives a group text message from a phone (e.g., sendercomputing device 120) directed to it and a third party (e.g., recipientcomputing device 130). The financial institution server determines whosent the text, a payment account associated with the sender, and paymentinstructions in the group text. The financial institution server alsodetermines contact information for the third-party and requests paymentreception information (i.e., how the third-party wants to receive thefunds) from the third-party. The financial institution server maygenerate a dynamic webpage for receiving the information and transmitthe link to the third-party. Once the information is received, thefinancial institution server initiates the transfer from the paymentaccount to the third-party.

1. (canceled)
 2. A method of facilitating a transfer comprising:receiving, from a telephone number of a sender, a message directedtoward a telephone number of a transfer facilitator, and a telephonenumber of at least one targeted transfer recipient, the message beingsent according to a text-messaging protocol, the message beingassociated with a verification code for verifying an authenticity of atransfer request; generating, in response to receiving the message, adynamic webpage with fields for receiving payment reception information;identifying, based on the telephone number of the sender, the sender andthe payment account associated with the sender; parsing the groupmessage to identify the telephone number of the at least one targetedtransfer recipient and instructions for the transfer request;contacting, using a private message sent to the telephone number of theat least one recipient according to the text-messaging protocol, the atleast one recipient with instructions for receiving a payment from thesender, wherein the private message contains a link to the dynamicwebpage; receiving, from a recipient device of the at least onerecipient, the payment reception information including at least one of arecipient account or a payment method; and initiating, in accordancewith the instructions for the transfer request, the fund transfer fromthe sender to the at least one recipient from the payment accountassociated with the sender and based on the payment receptioninformation; and deleting the dynamic webpage in response to eitherreceiving the payment reception information or a timeout occurring. 3.The method of claim 2, further comprising: receiving, from therecipient, image data of an image of an identification of the recipient;and analyzing the image data to confirm an identify of the recipient. 4.The method of claim 2, wherein receiving payment reception informationcomprises: receiving, from the recipient, image data of an image of acheck; and extracting account information from the image data as thepayment reception information.
 5. The method of claim 2, wherein themessage is directed toward the telephone number of the transferfacilitator and the at least one recipient; and the method furthercomprises transmitting a confirmation to the transfer facilitatorresponsive to receiving a communication seeking confirmation of aninterpretation of the transfer request.
 6. The method of claim 5,wherein the header includes the contact information for each of the atleast one recipient and the body includes names associated withrespective transfer amounts corresponding to each of the at least onerecipient; and the method further comprises matching the names to thecontact information.
 7. The method of claim 2, wherein the fund transferoccurs without any further action from the sender.
 8. The method ofclaim 2, wherein the verification code is generated pseudo-randomly by afirst computing device associated with the sender.
 9. The method ofclaim 2, wherein the verification code comprises a hash value determinedas a result of an input of at least one element of a transfer amount, asender account information, at least one recipient contact information,or a payment account associated with the sender and verifying theauthenticity of the instructions for the transfer request furthercomprises comparing the verification code to a stored code or acalculated code prior to initiating a fund transfer from the sender tothe at least one recipient.
 10. A system comprising: one or moreprocessors; and a memory in communication with the one or moreprocessors and storing instructions that, when executed by the one ormore processors, are configured to cause the system to: implement aconversational bot for facilitating transfer requests; receive, from atelephone number of a sender, a telephony message addressed to atelephone number associated with the conversational bot and a recipienttelephone number associated with a recipient, the telephony messagecomprising a funds transfer request from the sender to the recipient anda verification code for verifying an authenticity of a transfer request;generate, responsive to receiving the telephony message, a dynamicwebpage with fields for receiving payment reception information; parsethe message to identify the telephone number associated with therecipient and instructions for the transfer request; output, to therecipient based on the telephone number associated with the recipient, apayment recovery message requesting information on delivering payment tothe recipient, a body of the payment recovery message being determinedby the conversational bot, the payment recovery message comprising alink to the dynamic webpage; receive, from the recipient, the paymentreception information; initiate, in accordance with the funds transferrequest, the fund transfer from the sender to the recipient based on thepayment reception information; identify, from the message, the telephonenumber of the sender; determine an identity of the sender based on thetelephone number of the sender, wherein the sender has a personalaccount associated with the system, and the recipient does not have apersonal account associated with the system; and delete the dynamicwebpage in response to either receiving the payment receptioninformation or a timeout occurring.
 11. The system of claim 10, whereinthe telephony message is directed towards the telephone numberassociated with the conversational bot and a plurality of respectivetelephone numbers associated with a plurality of recipients, a body ofthe message comprises the funds transfer request to transfer respectivespecified amounts to each of the recipients, and the instructions arefurther configured to cause the system to analyze, using theconversational bot, the body of the message to determine an amount ofmoney to be transferred to the respective recipients.
 12. The system ofclaim 10, wherein the instructions are further configured to cause thesystem to: determine a payment account associated with the sender fortransferring funds to the recipient in accordance with the fundstransfer request.
 13. The system of claim 10, wherein the verificationcode comprises a hash value determined as a result of an input of atleast one element of a transfer amount, a sender account information, atleast one recipient contact information, or a payment account associatedwith the sender and verifying the authenticity of the instructions forthe transfer request further comprises comparing the verification codeto a stored code or a calculated code prior to initiating a fundtransfer from the sender to the at least one recipient.
 14. A method offacilitating a transfer comprising: receiving, at a transferfacilitator, a message configured to initiate a funds transfer, themessage sent using a text-messaging protocol and comprising averification code; parsing the message to identify transaction datacomprising a telephone number of a sender of the message, a telephonenumber of a recipient of the funds transfer, and an amount of the fundstransfer; identifying, based on the telephone number of the sender, asender name and a payment account associated with the sender; generatinga customized dynamic webpage with an input indicating the recipientaccepts the funds transfer; sending a private message to the telephonenumber of the recipient using the text-messaging protocol, the privatemessage including instructions for receiving the funds transfer from thesender and a link to the dynamic webpage; receiving, from the dynamicwebpage, recipient information including: the name of the recipient, thepayment account for the recipient, and the input accepting the fundstransfer; and initiating the funds transfer from the sender to therecipient from the payment account associated with the sender to thepayment account associated with the recipient; and deleting the dynamicwebpage in response to either receiving the recipient information or atimeout occurring.
 15. The method of claim 14, further comprising:sending a supplemental private message to the recipient comprisinglog-in credentials to provide access to the customized dynamic webpage.16. The method of claim 15, further comprising: receiving logincredentials from the recipient; determining that the login credentialsfrom the recipient match the login credentials sent to the recipient;and providing access to the dynamic webpage to the recipient.
 17. Themethod of claim 14, further comprising: receiving global positioningdata from a recipient device associated with the telephone number of therecipient.
 18. The method of claim 17, further comprising: confirmingthat the customized dynamic webpage is accessible based on the globalpositioning data received from the recipient device.
 19. The method ofclaim 14, wherein the timeout occurs after 12 hours.
 20. The method ofclaim 14, wherein the dynamic webpage is further configured to activatea camera associated with a recipient computing device to automaticallycapture and upload an image from which the payment account for therecipient is determined.
 21. The method of claim 14, wherein theverification code comprises a hash value determined as a result of aninput of at least one element of a transfer amount, a sender accountinformation, at least one recipient contact information, or a paymentaccount associated with the sender and verifying the authenticity of theinstructions for the transfer request further comprises comparing theverification code to a stored code or a calculated code prior toinitiating a fund transfer from the sender to the at least onerecipient.